Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

Configuring the class and entity cache

Progress Dynamics provides these session properties that you can use to configure the class and entity cache:

client_cache_directory — An absolute path where the client cache is generated and accessed. Setting this property eliminates one AppServer request (in AppServer configuration) otherwise required to obtain the relative path of the client cache based on the ry-clc product module.

You can use this property to help separate the development session from your run-time sessions.

auto_dump_entity_cache — Indication telling Dynamics if it is to dump the entity cache to disk at session shutdown. If this property is set to YES, at shutdown, Dynamics writes any entities in memory to disk. This allows you to reuse the entity information from the disk instead of going to the server with additional AppServer requests. The default value is YES.

This property primarily provides additional control to Progress Dynamics developers, where you typically set it to NO. In development sessions, you do not want entities cached, because you have to repeatedly delete the cache when you make changes to your entity information. However, in a run-time environment, you typically set it to YES to provide the performance benefits for the application.

StartupCacheClasses — A CVS list of classes that you want cached at startup, instead of fetching the class information when needed. Concentrating the caching of classes at startup allows faster rendering for containers during the greater part of the session duration.

Specify the "*" wild card to have Dynamics precache all the classes from the Repository at startup.

Note: Because a value of "*" results in a large amount of data movement during login, be careful when and how you use this option.